home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
500 MB Nyheder Direkte fra Internet 9
/
500 MB nyheder direkte fra internet CD 9.iso
/
start
/
zipped
/
dos
/
novell
/
c3295d_b.exe
/
IMAGE
/
________
/
SETUP.350
/
README.TXT
< prev
next >
Wrap
Text File
|
1995-12-12
|
24KB
|
620 lines
NETWARE CLIENT 32 FOR WINDOWS 95
OPEN BETA REFRESH RELEASE NOTES
12/12/95
CONTENTS
1.0 Welcome
2.0 Feature Enhancements in Open Beta Refresh
3.0 Upgrade issues
4.0 Protocol Support
5.0 Graphical Login
6.0 Client 32 Requestor Usage Notes
7.0 Printing Issues
8.0 ODI and NDIS LAN Driver Issues
9.0 Other Issues
10.0 International Issues
11.0 Troubleshooting
12.0 Trademarks
13.0 Disclaimer
1.0 Welcome
Welcome to the NetWare Client 32 for Windows 95 beta
test. We are excited about this product and appreciate
your support in testing this early software release.
Novell does not provide technical support to Open Beta participants.
If you experience problems with NetWare Client 32 for Windows 95,
send a description of the problem to CLIENT32BETA@NOVELL.COM. You
can also submit enhancement requests by sending a description of the
feature you would like in Client 32 to ENHCLIENT@NOVELL.COM.
You will not receive a direct response to your messages, but you can
find answers to frequently asked questions on NetWire
(http://netwire.novell.com/home/client/client32/faq.htm) or on
CompuServe (go novclient--download NOVCLI.EXE).
Novell will continue to provide technical support to registered beta
customers.
For information about NetWare Application Manager, see the README.NAL
file in the ADMIN\NAM\NLS\ENGLISH folder of the ADMIN2 disk.
2.0 Feature Enhancements in Open Beta Refresh
For more information on new features included in this release, search
for the feature in the SETUPNW.HLP help file.
2.1 Automatic Client Upgrade (ACU)
ACU enables network supervisors to upgrade client computers to
Client 32 as users log in to the network.
2.2 Support for Dial-Up Networking
Client 32 supports connections to Remote Access Servers (RAS)
over a modem, ISDN card, or X.25 connection.
2.3 Source Routing support for NDIS drivers.
You can enable source routing for NDIS drivers.
1. Double-click the "Network" icon in "Control Panel."
2. Double-click "IPX 32-bit Protocol for Novell NetWare Client 32" in
the "Network" properties dialog box.
3. Check "Enable Source Routing over NDIS" at the bottom of the
dialog box.
4. Close the properties dialogs.
2.4 System Policies
You can manage NetWare Client 32 for Windows 95 using System
Policy Editor (POLEDIT) and system policies. A template containing
client properties is available for use with POLEDIT.
2.5 Browser for Graphical Login
Users can browse the network for a server or tree during login.
2.6 Multiple Tree Support
Enables a client computer to authenticate and browse
multiple NetWare Directory Services (NDS) trees
and their resources.
3.0 Upgrade Issues
3.1 NetWare 3 Compatibility Issues
You should load SHORTAFX.NLM from the PATCHES\NW311 directory on the
Admin diskette. See the instruction in section 6.3.2 for information
on loading these patches.
3.2 NetWare 2.2 Compatibility Issues
There are known issues using Briefcase, Explorer, and Network
Neighborhood. These issues will be resolved in a future release.
Basic login and utilities are supported for NetWare 2.2.
4.0 Protocol Support
4.1 TCP/IP Support
NetWare Client 32 for Windows 95 does not include a TCP/IP stack.
Client 32 Setup does not move TCP/IP parameters from NET.CFG to the
registry.
4.2 SNMP Support
Currently, printers, modems, and tape drives are not shown in the Host
Resources MIB Device Table.
4.3 File and Print Sharing for NetWare Networks Not Supported
Client 32 does not support "File and printer sharing for NetWare
Networks" (emulated NCP file and print services). Client 32 does
support "File and printer sharing for Microsoft Networks" that
accompanies the [Microsoft] Client for Microsoft Networks.
4.4 Named Pipes Support
There is no Named Pipes support for Novell OS/2 Named Pipes Services.
DOSNP.EXE cannot be loaded under Windows 95.
4.5 NetBIOS Support
NetBIOS applications are supported through the components provided
by Windows 95. You must enable this component through the properties
of the "IPX/SPX-compatible Protocol."
4.6 Multiple Board Support
Client32 detects when there is more than one board available and
dynamically determines which board it should use to communicate with
NetWare Servers.
Client32 only supports simultaneous connections to two separate
networks through the use of the RAS feature. RAS logs you off the
network when you establish a RAS connection and allows you to login
to the remote network. Once the connection is established, you cannot
login to the local network until you have disconnected your RAS
connection.
5.0 Graphical Login
5.1 Closing MS-DOS Prompt Windows
If you use a login script that contains a "#" command (such as
CAPTURE), the MS-DOS Prompt window mignt not close after the login
script completes. You can configure the MS-DOS Prompt window to
close automatically by doing the following:
1. Open an MS-DOS Prompt window.
2. From the window pop-down menu, click "Properties".
3. On the "Program" page, check "Close on exit."
4. Click "OK."
5.2 Avoid Using Batch Files with Pause Commands
The computer might hang while processing a batch file called from a
login script that has a command to pause the display. Commands that
pause the display include "PAUSE,""|MORE," and "/P." Client 32
does not hang if PAUSE commands are directly in login scripts.
5.3 Avoid Multi-Tasking while Logging In
Although Windows 95 allows you to perform other tasks while Client 32
process a login script, you should avoid doing so. For example,
opening Network Neighborhood while Client 32 is processing a login
script causes the Multi-Provider Router (MPR.EXE) to page fault.
6.0 Client 32 Requestor Usage Notes
6.1 Running Out of Server Disk Space
Client 32 saves files to the client computer's memory before writing
them to the server. This enables applications to continue working
while Client 32 saves data to the network in the background.
If you save a file to a network folder that does not have a enough
space to store the file, Client 32 reports that the network folder
is out of disk space, even though the application you saved the file
from reported that it saved the file successfully.
If this happens, you should save the file to another folder or save
the file to the same folder again after creating more space in the
folder. The following describes a scenario that illustrates this
problem:
1. An application writes data to a network drive.
2. Client 32 returns a success code to the application. The
application continues with other processes.
3. Client 32 begins transferring the data from the client computer's
cache memory to the server.
4. During the transfer, the server returns an OUT_OF_DISK_SPACE
error code to Client 32.
5. Client 32 reports the following status message on the client
computer:
"Out of disk space writing file <filename> to server <server name>."
"Try deleting some files before continuing."
"Warning: You will lose data if you hit 'Cancel'."
If you click "Retry" after making room on the folder, Client
32 writes the file to the folder with no loss of data. If you
click "Cancel," Client 32 ends the data transfer process and the
file is not saved on the server. The user should save the file to
another folder to avoid losing the file.
If you want Client 32 to save data directly to a network drive, you
set the Cache Writes parameter to "off" in the "Novell NetWare Client
32 Properties" dialog box. For more information, see the Cache Writes
topic in the NWCFG95.HLP help file.
6.2 Long Filename Support
6.2.1 Long Filename Support on NetWare 4.1
To enable long filename support on NetWare 4.1 servers:
1. Copy PM410.NLM and NSWILDFX.NLM from the PATCHES\NW410 folder
on the Admin diskette to the SYS:\SYSTEM folder on the server.
2. At the server console prompt, enter
LOAD OS2.NAM
3. At the server console prompt, enter
LOAD PM410
LOAD NSWILDFX
4. At the server console prompt, enter
ADD NAME SPACE OS2 TO VOLUME <volume>
5. Add the load commands for the OS/2 name space
to the STARTUP.NCF file and the patches to
the AUTOEXEC.NCF file.
6.2.2 Long Filename Support on NetWare 3.11
To enable long filename support on NetWare 3.11:
1. Copy PATCHMAN.NLM, SHORTAFX.NLM, and
OS2OPNFX.NLM from the PATCHES\NW311 folder
on the Admin diskette to the SYS:\SYSTEM
folder on the server.
2. Load the OS/2 name space.
At the server console prompt, enter
LOAD OS2.NAM
3. Load the patches.
At the server console prompt, enter
LOAD PATCHMAN
LOAD SHORTAFX
LOAD OS2OPNFX
4. Add the OS/2 name space to the server volumes.
At the server console prompt, enter
ADD NAME SPACE OS2 TO VOLUME <volume>
5. Add the load commands for the OS/2 name space
to the STARTUP.NCF file and the patches to
the AUTOEXEC.NCF file.
NOTES
PM410.NLM and PATCHMAN.NLM are the server patch
managers.
6.3 Borland C++
The Borland C++ 4.5 MAKE utility does not work correctly when the
Borland executable files are located on a network search drive. The
MAKE utility builds an invalid path for other Borland utilities
called in the make file. You can work around this problem by mapping
the search drive as a root. For example:
MAP INS R S1:=<server>/SYS:TOOLS/BC45/BIN
7.0 Printing Issues
7.1 NPRINTER
Computers cannot run the NetWare 3 or NetWare 4 NPRINTER or
terminate-and-stay-resident (TSR) programs under Windows 95. A
32-bit NPRINTER.EXE is currently under development.
7.2 Print Capture on Windows 95
Windows 95 does not require local ports to be captured to send print
jobs to a network printer. You can send print jobs to an LPT port or
to a network printer device. Capture commands are global in Windows
95, but the settings for captured ports are separate from the
settings for network printer devices.
7.3 NDS Print Queues
NDS print queues are not displayed in the browse dialog boxes for
the Add Printer Wizard. To install a printer from an NDS print
queue, find the queue using Network Neighborhood or Explorer.
Double-click the print queue icon and use the Add Printer Wizard to
install the printer on your computer.
Microsoft offers a file that displays NDS print queues in Windows 95
browse dialog boxes. You can download the file from these Internet
sites:
http://www.microsoft.com/windows/software/shellupd.htm
ftp://ftp.microsoft.com/peropsys/Win_News/FreeSoftware/shellupd.exe
7.4 HP JetAdmin Support
The HP JetAdmin (NetWare Support) service contains calls to the
registry that exist only when the Microsoft NetWare Client is loaded.
If you want to use HP JetAdmin with Client 32, install JetAdmin for
Windows 3.x on your Windows 95 computer. Novell is working with HP
to supply a JetAdmin service for Windows 95.
8.0 ODI and NDIS LAN Driver Issues
See SETUPNW.HLP for a list of ODI LAN drivers included in this release.
8.1 Using LAN Drivers Other than Those Included with This Release
If you have a LAN driver for your LAN adapter that is newer
than the one included in this release, you can install the driver
during Client 32 Setup. You can also update the driver after
Client 32 is installed.
To install a third-party ODI LAN driver during Setup:
1. Copy the driver to the \ENGLISH folder (or the install folder you
created) before installing Client 32.
2. Follow the directions in the next section for installing
3rd-party LAN drivers.
To update a LAN driver after installing Client 32:
1. Do either of the following:
* For 32-bit (*.LAN) drivers, copy the new driver to the client
computer's NOVELL\CLIENT32 folder.
* For a 16-bit (*.COM) driver, copy the new driver to the client
computer's NOVELL\NWCLIENT folder.
2. Follow the directions in the next section for installing
third-party LAN drivers.
8.2 Installing 3rd-Party LAN Drivers
If you want to use an ODI LAN driver from a vendor other than Novell,
you need to specify the driver in the Client 32 Setup initialization
file.
If you have a newer driver than the one provided with this
release, copy the driver to the Client 32 install directory. (See the
previous section.)
To install a 3rd-party ODI LAN driver:
1. Before running Client 32 Setup, open NWSETUP.INI in a text
editor.
2. Search for the .INF file that corresponds to LAN driver you want
to use. The .INF files for third-party LAN drivers are named
ODIxxxx.INF, where "xxxx" is the manufacturer of the network
adapter. For example, ODI3COM.INF.
3. Delete the semicolon at the front of the line.
4. Save your changes and exit the editor.
5. Run Client 32 Setup.
8.3 Do Not Remove Novell ODINSUP
Do not remove Novell ODINSUP from the Network control panel, unless
you know the ODI adapter it is bound to. Removing Novell ODINSUP
also removes NetWare Client 32 for Windows 95 if there is only one
adapter in use.
8.4 16-bit ODI Driver Limitations
Windows 95 might remove support for 16-bit drivers if you remove or
update a 16-bit driver. If you have another LAN adapter using a
16-bit driver, the driver might fail to load after you boot the computer.
For example, if your computer has two adapters using 16-bit ODI
drivers, and you switch one of the LAN adapters to use a 32-bit
driver, the remaining 16-bit driver might not load.
To correct this problem, open the AUTOEXEC.BAT file and add lines
to load LSL.COM and NESL.COM. Add these lines before the line that
loads the 16-bit driver. For example:
LSL.COM
NESL.COM
N16ODI.COM
NE2000.COM
If two or more adapters use the same 16-bit ODI driver,
Windows 95 loads the driver from AUTOEXEC.BAT only once. You
should edit AUTOEXEC.BAT and copy the driver load command so that
AUTOEXEC.BAT loads the driver once for each adapter.
8.5 Windows 95 Loads a LAN Driver You Don't Want to Use
When Windows 95 detects a new LAN adapter in the computer, it
installs a driver for the adapter based on a preset list of drivers.
If Windows 95 loads a driver other than the one you want to use,
rename the unwanted driver's .INF file. To find the .INF file to
rename, search for the .INF file that matches the LAN driver's
provider, manufacturer, and device ID.
8.6 NetWare Server Drivers
Client 32 does not support NetWare server drivers shipped with
NetWare 3.11. Some LAN drivers shipped with NetWare 3.11 and 4.1 are
compatible with Client 32. Novell has tested only the drivers
included in this release.
8.7 NDIS Drivers
Client 32 setup installs ODI LAN drivers. If you want to use NDIS
drivers on your computer, you can switch to NDIS drivers by doing
the following:
1. Open NWSETUP.INI in a text editor. If you have run Client 32 Setup,
NWSETUP.INI is in the NOVELL\CLIENT32 folder. If you have not
installed Client 32, NWSETUP.INI is in the ENGLISH folder.
2. Find the [INF Files] section.
3. Add a semicolon (;) to the front of each line that lists an ODI*.INF
file in the [INF Files] section.
4. Add a semicolon to the front of each line that lists an NE*.INF
file.
5. Add a semicolon to the front of the NTR2000.INF line.
6. Save your changes and exit the editor.
7. Change to the WINDOWS\INF folder.
8. Rename the .INF files you commented out of NWSETUP.INI in Steps
3, 4, and 5 to an extension other then .INF.
NOTE: You can replace the ODI driver by adding semicolons to lines
you edited in Step 3 and reinstalling Client 32.
8.8 Plug and Play ISA LAN Adapters
ODI currently does not support Plug And Play ISA LAN adapters on
Windows 95. Use the NDIS drivers for these adapters.
9.0 Other Issues
9.1 Refresh NWPOPUP.EXE
If you receive a NetWare critical error message and your system
appears to be hung, do the following:
1. If you are unable to regain control of the system, reboot the
computer.
2. Copy NWPOPUP.EX_ from DISK 2 to the WINDOWS\SYSTEM folder.
3. Press <Ctrl>+<Alt>+<Del> and end the NWPOPUP.EXE task.
4. Delete the old NWPOPUP.EXE from your Windows 95 system folder.
5. Expand NWPOPUP.EX_ by typing "EXPAND NWPOPUP.EX_ NWPOPUP.EXE" at
a DOS prompt.
6. Restart your computer.
9.2 Task-Switching and GroupWise Client for DOS
Client 32 does not support task-switching in DOS. To run the
GroupWise Client for DOS, use the /da command line switch to disable
task-switching in DOS.
9.3 NDOS Command Shell Compatibility
NetWare Client 32 for Windows 95 is compatible with NDOS versions
distributed with The Norton Utilities from Symantec, versions 7.00 and
later only.
10.0 International Issues
10.1 Unicode Tables Not Found
If you run an international version of Windows 95, you might see the
following message during startup:
NWDRV-3.00.30: Initialization of the Unicode tables failed
Country id = XXX and code page = YYY
All NetWare Directory Services functions are disabled.
You can add a code page override in your WIN.INI file to avoid this
problem by doing the following:
1. Open WIN.INI in a text editor.
2. Search for the iCountry= setting in the [intl] section and make
sure the settings is correct for your locale.
3. Find or create the [NetWare] section.
4. On a new line in the [NetWare] section, type "NWCodepage=".
5. Type the number of the code page your country code uses after the
"=". See the table below for information on code page numbers.
6. Restart the computer.
For example, on a traditional Chinese system in Taiwan, you might
need to have the following sections in the WIN.INI file:
[NetWare]
NWCodepage=950
[intl]
iCountry=88
The following are example country code and code page values:
Country Code
Code Country Page
81 Japan 932
82 Korea 949
86 China 936
88 Taiwan 950
If you find this problem in other countries, please send a message
to client32beta@novell.com.
10.2 Unicode Tables for Text-Mode Utilities
If you have difficulties running NetWare text-mode utilities (such
as FILER, PCONSOLE, and NETADMIN) at a Windows 95 MS-DOS Prompt,
copy the Unicode mapping tables to the following directories:
SYS:LOGIN\NLS
SYS:PUBLIC\NLS
SYS:SYSTEM\NLS
For example, for running a traditional Chinese system in Taiwan
attached to a Novell NetWare 4.1 server, you could do the
following:
MAP T:=SYS:
CD C:\WINDOWS\NLS
COPY *.088 T:\LOGIN\NLS
COPY *.088 T:\PUBLIC\NLS
COPY *.088 T:\SYSTEM\NLS
This procedure is not applicable to NetWare 2 and
NetWare 3 servers, which do not use Unicode files.
10.3 Text-mode Utilities Might Not Display Correctly
Text-mode utilities (such as FILER, PCONSOLE, and
NETADMIN) might not display correctly for Korea,
China, and Taiwan. The overlay files needed to correct this problem
will be provided in a future release.
10.4 People's Republic of China
The Unicode mapping files for PRC, country code 86, are
not available in this Open Beta. If you are using PRC
Windows 95, send E-mail directly to Novell at
client32beta@novell.com for information on receiving
these files.
11.0 Troubleshooting
11.1 System Policies Do Not Work Properly
Indication: When users logs in, duplicate entries appear in the
Start menu and some shortcuts have truncated names.
Exlanation: The OS/2 name space module is not loaded on the
user's default server. NetWare servers require the OS/2 name space
module, OS2.NAM, to provide support for Windows 95 long file names.
For the final release, Client 32 will detect that the server does
not support long file names and will not load the user's profile
information. For this open beta, see section 6.3 for information on
loading OS/2 name space.
11.2 Resolving Application Communication Problems
Complete the following steps if your IPX/SPX applications are not functioning:
1. Determine the frame type used for IPX communications at your site
by either asking your network manager or by examining a NET.CFG
file on another computer.
2. Select "Network" from the "Control Panel" and double click "IPX
32-bit Protocol for Novell Client 32."
3. Select the Advanced IPX page.
4. Check "Primary logical board" and select a frame type to match
the frame type used on your network. Type a frame type name if
the frame type that you need is not listed.
5. Click "OK" until you exit the "Network" dialog box.
6. Restart your computer and try running the application again.
12.0 Trademarks
12.1 Novell Trademarks
Novell and NetWare are registered trademarks of
Novell, Inc. in the United States and other
countries.
Client 32, GroupWise, Internetwork Packet Exchange and IPX, IPX/SPX,
NetWare 3, NetWare 4, NetWare Client, Client 32 NetWare Core
Protocol and NCP, NetWare Directory Services and NDS, NetWare
Loadable Module and NLM, Open Data-Link Interface and ODI, Personal
NetWare, Sequenced Packet Exchange and SPX, and Virtual Loadable
Module and VLM are trademarks of Novell, Inc.
NetWire is a registered service mark of Novell, Inc.
12.2 Third-Party Trademarks
Borland is a registered trademark of Borland International, Inc.
CompuServe is a registered trademark of CompuServe Incorporated. HP
is a registered trademark of Hewlett-Packard Company. Intel is a
registered trademark of Intel corporation. OS/2 is a registered
trademark of International Business Machines Corporation. Microsoft,
MS, MS-DOS, and Windows are registered trademarks of Microsoft
Corporation. Symantec and The Norton Utilities are registered
trademarks of Symantec Corporation. Unicode is a registered
trademark of Transoft Ltd.
13.0 Disclaimer
Novell, Inc., makes no representations or warranties
with respect to any NetWare software, and specifically
disclaims any express or implied warranties of
merchantability, title, or fitness for a particular
purpose. Distribution of any NetWare software is
forbidden without the express written consent of
Novell, Inc. Further, Novell reserves the right to
discontinue distribution of any NetWare software.
Novell is not responsible for lost profits or revenue,
loss of use of the software, loss of data, costs of
recreating lost data, the cost of any substitute
equipment or program, or claims by any party other
than you.
Novell strongly recommends a backup be made before
any software is installed. Technical support for this
software may be provided at the discretion of Novell.